🔍 Problem
PR #3104 (commit 666ce69) swapped our generic tool-banner logic for a short hard-coded switch. As a result, unknown MCP tools were reduced to showing only a single argument key ("directory") and lost both the tool name context.

✨ What's Fixed

🛠 Implementation

ToolCallWithResponse.tsx

• Simplified tool description logic with clean, focused displays
• Each switch-case branch returns descriptive text without prefixes
• Default branch builds clean ToolName keys fallback for unknown tools
• Maintains all existing tool-specific display logic

ResponseStylesSection.tsx

• Uses direct localStorage calls consistent with rest of codebase
• Focuses solely on Concise/Detailed response style selection

Removed Infrastructure

• Eliminated feature-specific localStorage utilities that were solving theoretical problems
• Maintains consistency with 20+ other files that use direct localStorage calls successfully

✅ Testing
Verified that:

• Known tools show clean descriptions: running command
• Unknown tools fall back to generic display: ToolName arguments
• Response styles functionality works identically to before
• TypeScript compilation and ESLint checks pass
• No breaking changes to existing functionality

🎯 Result
Tool banners are now clean and focused while preserving full functionality:

• Before: [Extension: developer] writing /path/to/file.ts
• After: writing /path/to/file.ts

This addresses the core issue from #3104 with a simple, maintainable solution that doesn't add UI complexity or feature-specific infrastructure.